chore(6938): migrate settings-search InputAdornment from MUI v4 → v5#41957
chore(6938): migrate settings-search InputAdornment from MUI v4 → v5#41957
Conversation
Agent-Logs-Url: https://github.com/MetaMask/metamask-extension/sessions/497fc9c3-dfc1-4709-97f9-b58f5063d703 Co-authored-by: MajorLift <34228073+MajorLift@users.noreply.github.com>
|
@metamaskbot update-policies |
|
No policy changes |
…ngs-search-inputadornment-v4-v5
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Caution MetaMask internal reviewing guidelines:
|
|
@metamaskbot update-policies |
|
Policies updated. Tip Follow the policy review process outlined in the LavaMoat Policy Review Process doc before expecting an approval from Policy Reviewers. 👀 lavamoat/browserify/beta/policy.json changes differ from lavamoat/browserify/main/policy.json changes |
…ngs-search-inputadornment-v4-v5
✨ Files requiring CODEOWNER review ✨📜 @MetaMask/policy-reviewers (14 files, +1293 -621)
Tip Follow the policy review process outlined in the LavaMoat Policy Review Process doc before expecting an approval from Policy Reviewers. |
|
Builds ready [a033f4c]
⚡ Performance Benchmarks (Total: 🟢 0 pass · 🟡 0 warn · 🔴 0 fail)
Bundle size diffs
|



Part of the broader MUI v4 → v5 migration. Updates the single
@material-ui/core/InputAdornmentusage in the settings search component to@mui/material/InputAdornment. TheInputAdornmentAPI is unchanged between versions.Changes
settings-search.js— swap import path:package.json— add@mui/material: "^5.14.0"as a direct dependency (@mui/materialv5.18.0 was already present as a transitive dep; this makes the direct usage explicit)yarn.lock— one-line update to register@mui/materialunder the root workspace metadata (no new resolution required)